Software User's Guide Version 3.4

Configuring Change Management

This chapter describes the Change management configuration commands. It includes the following sections:

"Accessing the Change Management Configuration Environment"
"Change Management Configuration Commands"

Accessing the Change Management Configuration Environment

To enter the change management configuration command environment, use the CONFIG boot command. When the device's software is initially loaded, it is running in the OPCON process, signified by the * prompt. From the * prompt:

Enter talk 6.
At the Config> prompt, type boot.

To return to the CONFIG process, type exit.

Change Management Configuration Commands

This section describes the Change Management Configuration commands. Each command includes a description, syntax requirements, and an example. Table 5 summarizes the Change Management Configuration commands.

After accessing the Change Management Configuration environment, enter the configuration commands at the Boot config> prompt.

Table 5. Change Management Configuration Commands

Command Function
? (Help) Displays all the commands available for this command level or lists the options for specific commands (if available). See "Getting Help".
Add Adds an optional description to a configuration file.
Copy Copies boot files and configuration files to or from banks.
Describe Displays information about the stored loadfile images.
Disable Turns off various change management functions.
Enable Turns on various change management functions.
Erase Erases a stored image or a configuration file.
List Displays information about configuration files and scheduled load information.
Lock Prevents the device from overwriting the selected configuration with any other configuration.
Set Selects code bank and configuration to be used.
Tftp Initiates TFTP file transfers between the IBM 2216 and remote servers.
Timedload Schedules a load into the device on a specific day and time, cancels a scheduled load, or displays scheduled load information.
Unlock Removes the lock from a configuration allowing the configuration to be updated by the device.
Update Firmware Installs the Firm.ld load module that you have received on either Bank A or Bank B of your 2216
Exit Returns you to the previous command level. See "Exiting a Lower Level Environment".

Command	Function
? (Help)	Displays all the commands available for this command level or lists the options for specific commands (if available). See "Getting Help".
Add	Adds an optional description to a configuration file.
Copy	Copies boot files and configuration files to or from banks.
Describe	Displays information about the stored loadfile images.
Disable	Turns off various change management functions.
Enable	Turns on various change management functions.
Erase	Erases a stored image or a configuration file.
List	Displays information about configuration files and scheduled load information.
Lock	Prevents the device from overwriting the selected configuration with any other configuration.
Set	Selects code bank and configuration to be used.
Tftp	Initiates TFTP file transfers between the IBM 2216 and remote servers.
Timedload	Schedules a load into the device on a specific day and time, cancels a scheduled load, or displays scheduled load information.
Unlock	Removes the lock from a configuration allowing the configuration to be updated by the device.
Update Firmware	Installs the Firm.ld load module that you have received on either Bank A or Bank B of your 2216
Exit	Returns you to the previous command level. See "Exiting a Lower Level Environment".

Add

Use the add command to add an optional description to a configuration file.

Syntax:

add: configuration file description
: load image description

Example: Boot config> add

+------ BankA -----------+--------- Description ----------+------ Date -------+
| IMAGE - NONE           |                                | 01 Jan 1970 00:01 |
| CONFIG 1 - AVAIL       | test config for pubs           | 01 Jan 1970 01:26 |
| CONFIG 2 - AVAIL   *   | test config for pubs           | 01 Jan 1970 01:13 |
| CONFIG 3 - AVAIL       |                                | 01 Jan 1970 01:39 |
| CONFIG 4 - AVAIL       |                                | 01 Jan 1970 01:52 |
+------ BankB -----------+--------- Description ----------+------ Date -------+
| IMAGE - ACTIVE         |                                | 01 Jan 1970 00:30 |
| CONFIG 1 - AVAIL       | test config for pubs           | 01 Jan 1970 00:54 |
| CONFIG 2 - AVAIL       |                                | 01 Jan 1970 00:01 |
| CONFIG 3 - AVAIL       |                                | 01 Jan 1970 00:14 |
| CONFIG 4 - ACTIVE  *   |                                | 01 Jan 1970 00:24 |
 
+------------------------+--------------------------------+-------------------+
  * - Last Used Config      L - Config File is Locked
 
 
Select the source bank:  (A, B): [A] 
Select the source configuration:  (1, 2, 3, 4): [1] 3
Enter the description of the file: () New config for today
 
Attempting to set description for bank A configuration 3.
 
Operation completed successfully.
 
 
Boot config>list
+------ BankA -----------+--------- Description ----------+------ Date -------+
| IMAGE - NONE           |                                | 01 Jan 1970       |
| CONFIG 1 - AVAIL       | test config for pubs           | 01 Jan 1970 00:58 |
| CONFIG 2 - AVAIL   *   | test config for pubs           | 01 Jan 1970 01:13 |
| CONFIG 3 - NONE        | New config for today           | 09 Jan 1970 00:58 |
| CONFIG 4 - AVAIL       |                                | 01 Jan 1970 01:05 |
+------ BankB -----------+--------- Description ----------+------ Date -------+
| IMAGE - ACTIVE         |                                | 01 Jan 1970       |
| CONFIG 1 - AVAIL       | test config for pubs           | 01 Jan 1970 00:54 |
| CONFIG 2 - AVAIL       |                                | 01 Jan 1970 00:01 |
| CONFIG 3 - AVAIL       |                                | 01 Jan 1970 00:14 |
| CONFIG 4 - ACTIVE  *   |                                | 01 Jan 1970 00:24 |
 
+------------------------+--------------------------------+-------------------+
  * - Last Used Config      L - Config File is Locked
 
  Auto-boot mode is enabled. Fast-boot mode is disabled.

Copy

Use the copy command to copy configuration files and load images to and from the banks.
Note: You can use the copy bank command to copy an entire bank, which is convenient if you want to use one bank as a backup for another bank.

Syntax:

copy: bank
: configuration file

Example:

Boot config>copy bank
 
+------ BankA -----------+--------- Description ----------+------ Date -------+
| IMAGE - PENDING        |                                | 22 Jan 1999 17:15 |
| CONFIG 1 - AVAIL       |                                | 05 Feb 1999 13:42 |
| CONFIG 2 - PENDING *   |                                | 22 Jan 1999 17:24 |
| CONFIG 3 - AVAIL       |                                | 05 Feb 1999 13:42 |
| CONFIG 4 - AVAIL       |                                | 05 Feb 1999 13:42 |
+------ BankB -----------+--------- Description ----------+------ Date -------+
| IMAGE - AVAIL          |                                | 05 Feb 1999 13:39 |
| CONFIG 1 - CORRUPT     |                                | 05 Feb 1999 13:39 |
| CONFIG 2 - AVAIL       |                                | 05 Feb 1999 13:39 |
| CONFIG 3 - AVAIL       |                                | 05 Feb 1999 13:39 |
| CONFIG 4 - AVAIL       |                                | 05 Feb 1999 13:39 |
+------------------------+--------------------------------+-------------------+
  * - Last Used Config      L - Config File is Locked
 
 Auto-boot mode is disabled.   Fast-boot mode is disabled.
 
Select the source bank:  (A, B): [A] A
Select the destination bank:  (A, B): [B] B
we are about to try copying configs
Copy SW configuration from: bank A, configuration 1
                         to: bank B, configuration 1.
/hd0/sys0/CONFIG0 --> /hd0/sys1/CONFIG0
 
Operation completed successfully.
Copy SW configuration from: bank A, configuration 2
                         to: bank B, configuration 2.
/hd0/sys0/CONFIG1 --> /hd0/sys1/CONFIG1
Operation completed successfully.
Copy SW configuration from: bank A, configuration 3
                         to: bank B, configuration 3.
/hd0/sys0/CONFIG2 --> /hd0/sys1/CONFIG2
 
Operation completed successfully.
Copy SW configuration from: bank A, configuration 4
                         to: bank B, configuration 4.
/hd0/sys0/CONFIG3 --> /hd0/sys1/CONFIG3
 
Operation completed successfully.
 
Copy SW load image from: bank A
                      to: bank B.
Operation completed successfully.
Boot config>

Example: Boot config>copy load

+------ BankA -----------+--------- Description ----------+------ Date -------+
| IMAGE - AVAIL          |                                | 01 Jan 1970 00:01 |
| CONFIG 1 - AVAIL       | test config for pubs           | 01 Jan 1970 01:26 |
| CONFIG 2 - AVAIL   *   | test config for pubs           | 01 Jan 1970 01:13 |
| CONFIG 3 - AVAIL       |                                | 01 Jan 1970 01:39 |
| CONFIG 4 - AVAIL       |                                | 01 Jan 1970 01:52 |
+------ BankB -----------+--------- Description ----------+------ Date -------+
| IMAGE - ACTIVE         |                                | 01 Jan 1970 00:01 |
| CONFIG 1 - AVAIL       |                                | 01 Jan 1970 00:14 |
| CONFIG 2 - AVAIL       |                                | 01 Jan 1970 00:01 |
| CONFIG 3 - AVAIL       |                                | 01 Jan 1970 00:37 |
| CONFIG 4 - ACTIVE  *   |                                | 01 Jan 1970 00:24 |
 
+------------------------+--------------------------------+-------------------+
  * - Last Used Config      L - Config File is Locked
 
 
Select the source bank:  (A, B): [A] b
Select the destination bank:  (A, B): [B] a
Copy SW load image from: bank B
                      to: bank A.
 
 
Operation completed successfully.

Example: Boot config>copy

+------ BankA -----------+--------- Description ----------+------ Date -------+
| IMAGE - CORRUPT        |                                | 01 Jan 1970 00:01 |
| CONFIG 1 - AVAIL       | test config for pubs           | 01 Jan 1970 01:26 |
| CONFIG 2 - AVAIL   *   | test config for pubs           | 01 Jan 1970 01:13 |
| CONFIG 3 - AVAIL       |                                | 01 Jan 1970 01:39 |
| CONFIG 4 - AVAIL       |                                | 01 Jan 1970 01:52 |
+------ BankB -----------+--------- Description ----------+------ Date -------+
| IMAGE - ACTIVE         |                                | 01 Jan 1970 00:01 |
| CONFIG 1 - AVAIL       |                                | 01 Jan 1970 00:14 |
| CONFIG 2 - AVAIL       |                                | 01 Jan 1970 00:01 |
| CONFIG 3 - AVAIL       |                                | 01 Jan 1970 00:37 |
| CONFIG 4 - ACTIVE  *   |                                | 01 Jan 1970 00:24 |
 
+------------------------+--------------------------------+-------------------+
  * - Last Used Config      L - Config File is Locked
 
 
Select the source bank:  (A, B): [A]
Select the source configuration:  (1, 2, 3, 4): [1]
Select the destination bank:  (A, B): [B]
 
Select the destination configuration:  (1, 2, 3, 4): [1]
Copy SW configuration from: bank A, configuration 1
                         to: bank B, configuration 1.
/hd0/sys0/CONFIG0 --> /hd0/sys1/CONFIG0
 
Operation completed successfully.

If the copy fails you may receive one of the following messages:

Error: Active bank cannot be overwritten or erased.: You attempted to copy a configuration into the bank currently in use by the IBM 2216.
Error: File copy failed.: This condition occurs when the copy operation fails for reasons other than copying to the active configuration. The most common cause is specifying the same source and destination configurations. When you list (see "List") the configurations, CORRUPT appears next to the bank that is damaged.

Describe

Use the describe command to display information about a stored image.

Syntax: describe

Example: Boot config>describe

+-------------------------+-------------------------+
|         BANK A          |         BANK B          |
| Product ID -   2216-MAS | Product ID -   2216-MAS |
| Version   3 Release   2| Version   3 Release   2  |
| Mod       0 PTF       0 | Mod       0 PTF       0 |
| Feat.  2822 RPQ       0 | Feat.  2822 RPQ       0 |
| Date        31 Dec 1996 | Date        31 Dec 1996 |
+-------------------------+-------------------------+

Disable

Use the disable command to turn off various change management functions.

Syntax:

disable: auto-boot
: fast-boot

auto-boot

Disabling auto-boot causes the device boot sequence to stop at the service recovery interface, without running the device operational code. The default auto-boot mode is "enabled".

Example:

Boot config>disable auto-boot
Auto-boot mode is now disabled

fast-boot

Disabling fast-boot causes the device to run diagnostic tests when the device is booting during a power-on or a software reload. This provides better hardware error detection but results in slower boot times. This is the default mode, and is recommended whenever the device is in a production environment.

Enable

Use the enable command to turn on various change management functions.

Syntax:

enable: auto-boot
: fast-boot

auto-boot

Enabling auto-boot causes the device boot to the device operational code without stopping at the service recovery interface. The default auto-boot mode is "enabled"

Note:

To enable auto-boot mode using this command, you must also have unattended mode selected in the firmware.

fast-boot

Enabling fast-boot causes the device to skip diagnostic tests when the device is booting during a power-on or a software reload. This reduces hardware error detection but results in faster boot times. The default mode is "disabled," which is recommended whenever the device is in a production environment.

Example:

Boot config>enable fast-boot
Fast-boot mode is now enabled

Erase

Use the erase command to erase a stored image or a configuration file.

Syntax:

erase: configuration [file]
: load [image]

config or load: Erases a configuration file or a load image. Enter the config number to be erased after the erase command.

Example: Boot config>erase load

+------ BankA -----------+--------- Description ----------+------ Date -------+
| IMAGE - CORRUPT        |                                | 01 Jan 1970 00:01 |
| CONFIG 1 - AVAIL       | test config for pubs           | 01 Jan 1970 01:26 |
| CONFIG 2 - AVAIL   *   | test config for pubs           | 01 Jan 1970 01:13 |
| CONFIG 3 - NONE        |                                | 01 Jan 1970 00:58 |
| CONFIG 4 - AVAIL       |                                | 01 Jan 1970 00:39 |
+------ BankB -----------+--------- Description ----------+------ Date -------+
| IMAGE - ACTIVE         |                                | 01 Jan 1970 00:01 |
| CONFIG 1 - AVAIL       | test config for pubs           | 01 Jan 1970 00:54 |
| CONFIG 2 - AVAIL       |                                | 01 Jan 1970 00:01 |
| CONFIG 3 - AVAIL       |                                | 01 Jan 1970 00:14 |
| CONFIG 4 - ACTIVE  *   |                                | 01 Jan 1970 00:24 |
 
+------------------------+--------------------------------+-------------------+
  * - Last Used Config      L - Config File is Locked
 
 
Select the bank to erase:  (A, B): [A] a
Erase SW load image from bank A.
 
Operation completed successfully.
 
 
Boot config>list
+------ BankA -----------+--------- Description ----------+------ Date -------+
| IMAGE - NONE           |                                | 01 Jan 1970       |
| CONFIG 1 - AVAIL       | test config for pubs           | 01 Jan 1970 00:26 |
| CONFIG 2 - AVAIL   *   | test config for pubs           | 01 Jan 1970 01:13 |
| CONFIG 3 - AVAIL       |                                | 01 Jan 1970 00:58 |
| CONFIG 4 - AVAIL       |                                | 01 Jan 1970 00:39 |
+------ BankB -----------+--------- Description ----------+------ Date -------+
| IMAGE - ACTIVE         |                                | 01 Jan 1970       |
| CONFIG 1 - AVAIL       | test config for pubs           | 01 Jan 1970 00:54 |
| CONFIG 2 - AVAIL       |                                | 01 Jan 1970 00:01 |
| CONFIG 3 - AVAIL       |                                | 01 Jan 1970 00:14 |
| CONFIG 4 - ACTIVE  *   |                                | 01 Jan 1970 00:24 |
 
+------------------------+--------------------------------+-------------------+
  * - Last Used Config      L - Config File is Locked
 
  Auto-boot mode is enabled.  Fast-boot mode is disabled.

Example: Boot config>erase configuration

+------ BankA -----------+--------- Description ----------+------ Date -------+
| IMAGE - NONE           |                                | 01 Jan 1970 00:01 |
| CONFIG 1 - AVAIL       | test config for pubs           | 01 Jan 1970 00:26 |
| CONFIG 2 - AVAIL   *   | test config for pubs           | 01 Jan 1970 01:13 |
| CONFIG 3 - AVAIL       |                                | 01 Jan 1970 01:26 |
| CONFIG 4 - AVAIL       |                                | 01 Jan 1970 01:39 |
+------ BankB -----------+--------- Description ----------+------ Date -------+
| IMAGE - ACTIVE         |                                | 01 Jan 1970 00:01 |
| CONFIG 1 - AVAIL       | test config for pubs           | 01 Jan 1970 00:54 |
| CONFIG 2 - AVAIL       |                                | 01 Jan 1970 00:01 |
| CONFIG 3 - AVAIL       |                                | 01 Jan 1970 00:14 |
| CONFIG 4 - ACTIVE  *   |                                | 01 Jan 1970 00:24 |
 
+------------------------+--------------------------------+-------------------+
  * - Last Used Config      L - Config File is Locked
 
 
Select the source bank:  (A, B): [A]
Select the configuration to erase:  (1, 2, 3, 4): [1] 3
Erase SW configuration file from bank A, configuration 3.
 
Operation completed successfully.
 
 
Boot config>list
+------ BankA -----------+--------- Description ----------+------ Date -------+
| IMAGE - NONE           |                                |                   |
| CONFIG 1 - AVAIL       | test config for pubs           | 01 Jan 1970 00:14 |
| CONFIG 2 - AVAIL   *   | test config for pubs           | 01 Jan 1970 01:13 |
| CONFIG 3 - NONE        |                                | 01 Jan 1970 00:58 |
| CONFIG 4 - AVAIL       |                                | 01 Jan 1970 00:26 |
+------ BankB -----------+--------- Description ----------+------ Date -------+
| IMAGE - ACTIVE         |                                | 01 Jan 1970       |
| CONFIG 1 - AVAIL       | test config for pubs           | 01 Jan 1970 00:54 |
| CONFIG 2 - AVAIL       |                                | 01 Jan 1970 00:01 |
| CONFIG 3 - AVAIL       |                                | 01 Jan 1970 00:14 |
| CONFIG 4 - ACTIVE  *   |                                | 01 Jan 1970 00:24 |
 
+------------------------+--------------------------------+-------------------+
  * - Last Used Config      L - Config File is Locked
 
  Auto-boot mode is enabled.  Fast-boot mode is disabled.

Notice that the list command displays NONE by bank A, config 3.

If the erasure fails, a message indicating the failure appears on the console with the banks that failed.

List

Use the list command to display information about which load images and configuration files are available and active. This command may also be used to display boot options and scheduled load information.

Syntax:

list

Example: Boot config>list

+------ BankA -----------+--------- Description ----------+------ Date -------+
| IMAGE - AVAIL          |                                | 01 Jan 1970 00:01 |
| CONFIG 1 - AVAIL       | test config for pubs           | 01 Jan 1970 01:26 |
| CONFIG 2 - AVAIL   *   | test config for pubs           | 01 Jan 1970 01:13 |
| CONFIG 3 - NONE        |                                | 01 Jan 1970 00:58 |
| CONFIG 4 - AVAIL       |                                | 01 Jan 1970 00:39 |
+------ BankB -----------+--------- Description ----------+------ Date -------+
| IMAGE - ACTIVE         |                                | 01 Jan 1970 00:01 |
| CONFIG 1 - AVAIL       | test config for pubs           | 01 Jan 1970 00:54 |
| CONFIG 2 - AVAIL       |                                | 01 Jan 1970 00:01 |
| CONFIG 3 - AVAIL       |                                | 01 Jan 1970 00:14 |
| CONFIG 4 - ACTIVE  *   |                                | 01 Jan 1970 00:24 |
 
+------------------------+--------------------------------+-----------------+
  * - Last Used Config      L - Config File is Locked
  Auto-boot mode is enabled.  Fast-boot mode is disabled.
 
 
 Time Activated Load Schedule Information...
 
The device is scheduled to reload as follows.
 
Date:  June 26, 1997
Time:  16:30
The load modules are in bank A.
The configuration is CONFIG 1 in bank A.
Boot config>

The possible file status descriptors are:

ACTIVE: The file is currently loaded and is running on the 2216
AVAIL: This is a valid file that can be made ACTIVE.
CORRUPT: The file was damaged or not loaded into the 2216 completely. The file must be replaced.
LOCAL: The file will be used only on the next reload or reset. After the file is used, it will be placed in AVAIL state.
PENDING: This file will be loaded on the next reload, reset, or power-up of the 2216.

Lock

Use the lock command to prevent the device from overwriting the selected configuration with any other configuration.

Syntax:

lock

Example: Boot config>lock

+------ BankA -----------+--------- Description ----------+------ Date -------+
| IMAGE - NONE           |                                | 01 Jan 1970 01:03 |
| CONFIG 1 - AVAIL       | test config for pubs           | 01 Jan 1970 00:26 |
| CONFIG 2 - AVAIL   *   | test config for pubs           | 01 Jan 1970 01:13 |
| CONFIG 3 - NONE        |                                | 01 Jan 1970 00:58 |
| CONFIG 4 - AVAIL       |                                | 01 Jan 1970 00:26 |
+------ BankB -----------+--------- Description ----------+------ Date -------+
| IMAGE - ACTIVE         |                                | 01 Jan 1970 00:01 |
| CONFIG 1 - AVAIL       | test config for pubs           | 01 Jan 1970 00:54 |
| CONFIG 2 - AVAIL       |                                | 01 Jan 1970 00:01 |
| CONFIG 3 - AVAIL       |                                | 01 Jan 1970 00:14 |
| CONFIG 4 - ACTIVE  *   |                                | 01 Jan 1970 00:24 |
 
+------------------------+--------------------------------+-------------------+
  * - Last Used Config      L - Config File is Locked
 
Auto-boot mode is enabled.  Select the source bank:  (A, B): [A]
 
Select the source configuration:  (1, 2, 3, 4): [1] 4
Attempting to lock bank A and configuration 4.
 
Operation completed successfully.
 
 
Boot config>list
+------ BankA -----------+--------- Description ----------+------ Date -------+
| IMAGE - NONE           |                                | 01 Jan 1970       |
| CONFIG 1 - AVAIL       | test config for pubs           | 01 Jan 1970 00:13 |
| CONFIG 2 - AVAIL   *   | test config for pubs           | 01 Jan 1970 01:13 |
| CONFIG 3 - NONE        |                                | 01 Jan 1970 00:58 |
| CONFIG 4 - AVAIL   L   |                                | 01 Jan 1970 00:26 |
+------ BankB -----------+--------- Description ----------+------ Date -------+
| IMAGE - ACTIVE         |                                |                   |
| CONFIG 1 - AVAIL       | test config for pubs           | 01 Jan 1970 00:54 |
| CONFIG 2 - AVAIL       |                                | 01 Jan 1970 00:01 |
| CONFIG 3 - AVAIL       |                                | 01 Jan 1970 00:14 |
| CONFIG 4 - ACTIVE  *   |                                | 01 Jan 1970 00:24 |
 
+------------------------+--------------------------------+-------------------+
  * - Last Used Config      L - Config File is Locked
 
  Auto-boot mode is enabled.  Fast-boot mode is disabled.

Note:

Note that bank A config 4 is marked with an "L."

Set

Use the set command to select the code bank, the configuration to use, and the duration of use. The valid durations are:

once: The configuration is active for the next boot only.
always: The configuration is active for all subsequent boots until changed again.

Syntax:

set

Example: Boot config>set

+------ BankA -----------+--------- Description ----------+------ Date -------+
| IMAGE - NONE           |                                | 01 Jan 1970 01:03 |
| CONFIG 1 - AVAIL       | test config for pubs           | 01 Jan 1970 00:13 |
| CONFIG 2 - AVAIL   *   | test config for pubs           | 01 Jan 1970 01:13 |
| CONFIG 3 - NONE        |                                | 01 Jan 1970 00:58 |
| CONFIG 4 - AVAIL       |                                | 01 Jan 1970 00:26 |
+------ BankB -----------+--------- Description ----------+------ Date -------+
| IMAGE - ACTIVE         |                                | 01 Jan 1970 00:01 |
| CONFIG 1 - AVAIL       | test config for pubs           | 01 Jan 1970 00:54 |
| CONFIG 2 - AVAIL       |                                | 01 Jan 1970 00:01 |
| CONFIG 3 - AVAIL       |                                | 01 Jan 1970 00:14 |
| CONFIG 4 - ACTIVE  *   |                                | 01 Jan 1970 00:24 |
 
+------------------------+--------------------------------+-------------------+
  * - Last Used Config      L - Config File is Locked
 
 
Select the source bank:  (A, B): [A] b
 
Select the source configuration:  (1, 2, 3, 4): [1] 4
Select the duration to use for booting:  (once, always): [always]
Set SW to boot using bank B and configuration 4, always.
 
Operation completed successfully.
 
 
Boot config>list
+------ BankA -----------+--------- Description ----------+------ Date -------+
| IMAGE - NONE           |                                | 01 Jan 1970       |
| CONFIG 1 - AVAIL       | test config for pubs           | 01 Jan 1970 00:13 |
| CONFIG 2 - AVAIL   *   | test config for pubs           | 01 Jan 1970 01:13 |
| CONFIG 3 - NONE        |                                | 01 Jan 1970 00:58 |
| CONFIG 4 - AVAIL       |                                | 01 Jan 1970 00:26 |
+------ BankB -----------+--------- Description ----------+------ Date -------+
| IMAGE - ACTIVE         |                                | 01 Jan 1970       |
| CONFIG 1 - AVAIL       | test config for pubs           | 01 Jan 1970 00:54 |
| CONFIG 2 - AVAIL       |                                | 01 Jan 1970 00:01 |
| CONFIG 3 - AVAIL       |                                | 01 Jan 1970 00:14 |
| CONFIG 4 - ACTIVE  *   |                                | 01 Jan 1970 00:24 |
 
+------------------------+--------------------------------+-------------------+
  * - Last Used Config      L - Config File is Locked
 
   Auto-boot mode is enabled.  Fast-boot mode is disabled.

TFTP

Use the tftp command to initiate TFTP file transfers between the 2216 and remote servers.
Note: When you unzip an image, you will see multiple files ending in ".ld". Use the tftp get load modules command to get multiple load modules.

Syntax:

tftp get: config
: load modules
tftp put: config
: load single image
: load modules

Example: Boot config>tftp get load single

+------ BankA -----------+--------- Description ----------+------ Date -------+
| IMAGE - NONE           |                                | 01 Jan 1970 01:03 |
| CONFIG 1 - AVAIL       | test config for pubs           | 01 Jan 1970 00:01 |
| CONFIG 2 - AVAIL   *   | test config for pubs           | 01 Jan 1970 01:13 |
| CONFIG 3 - NONE        |                                | 01 Jan 1970 00:58 |
| CONFIG 4 - AVAIL       |                                | 01 Jan 1970 00:14 |
+------ BankB -----------+--------- Description ----------+------ Date -------+
| IMAGE - ACTIVE         |                                | 01 Jan 1970 00:01 |
| CONFIG 1 - AVAIL       | test config for pubs           | 01 Jan 1970 00:54 |
| CONFIG 2 - AVAIL       |                                | 01 Jan 1970 00:01 |
| CONFIG 3 - AVAIL       |                                | 01 Jan 1970 00:14 |
| CONFIG 4 - ACTIVE  *   |                                | 01 Jan 1970 00:24 |
 
+------------------------+--------------------------------+-------------------+
  * - Last Used Config      L - Config File is Locked
 
 
Specify the server IP address (dotted decimal): : [1.2.3.4] 192.9.200.1
Specify the remote file name: : (/u/bin) /usr/2216load/c200-rtr.img
Select the destination bank:  (A, B): [A] a
  TFTP SW load image
  get:   /usr/2216load/c200-rtr.img
  from:  192.9.200.1
  to:    bank A.
 
Operation completed successfully.

Note for Dynamic Loading of Software: All of the load modules in the specified directory will be retrieved as part of the load going into the bank. For loads for releases prior to Version 1, Release 2, this will be a single load module. For Version 1, Release 2 loads and later, this may be multiple load modules.
Example: Boot config>tftp get load modules

+------ BankA -----------+--------- Description ----------+------ Date -------+
| IMAGE - NONE           |                                | 01 Jan 1970 01:03 |
| CONFIG 1 - AVAIL       | test config for pubs           | 01 Jan 1970 00:01 |
| CONFIG 2 - AVAIL   *   | test config for pubs           | 01 Jan 1970 01:13 |
| CONFIG 3 - NONE        |                                | 01 Jan 1970 00:58 |
| CONFIG 4 - AVAIL       |                                | 01 Jan 1970 00:14 |
+------ BankB -----------+--------- Description ----------+------ Date -------+
| IMAGE - ACTIVE         |                                | 01 Jan 1970 00:01 |
| CONFIG 1 - AVAIL       | test config for pubs           | 01 Jan 1970 00:54 |
| CONFIG 2 - AVAIL       |                                | 01 Jan 1970 00:01 |
| CONFIG 3 - AVAIL       |                                | 01 Jan 1970 00:14 |
| CONFIG 4 - ACTIVE  *   |                                | 01 Jan 1970 00:24 |
 
+------------------------+--------------------------------+-------------------+
  * - Last Used Config      L - Config File is Locked
 
 
Specify the server IP address (dotted decimal): : [1.2.3.4] 192.9.200.1
Specify the remote modules directory: : (/u/bin) /usr/2216load/
Select the destination bank:  (A, B): [A] a
  TFTP SW load image
  get:   /usr/2216load/LML.ld
  from:  192.9.200.1
  to:    bank A.
 
Operation completed successfully.

Notes:

When putting files to a server:

Make sure that the files on the target server have the appropriate permissions that would allow anyone to write to those files. If not, the put operation will fail.
You must be aware of the files you are putting to the target server.To determine whether the image in the bank is a single module or multiple modules, use the describe command. A load prior to Version 1, Release 2 is a single module. Loads at Version 1, Release 2 or after are multiple modules.

Timedload

Use the timedload command to schedule a load on a device, cancel a scheduled load, or view scheduled load information.

This command allows you to load the device outside peak network traffic periods when support personnel may not be present.
Note: You may also use the Configuration Program to schedule a reload for a device, which is not affected by reloads or power outages. These circumstances would normally cause the reload to be lost. See the chapter "Using the Configuration Program" in Configuration Program User's Guide for Nways Multiprotocol and Access Services for details.

Syntax:

timedload: activate
: deactivate
: view

activate

Schedules a load on the device. You will be prompted for information for a time-activated load similar to the tftp get load and tftp get config commands. See "TFTP" for information about the parameters.

Time of day to load the router

Specifies the date and time to load the device. Specify the value as YYYYMMDDHHMM, where:

YYYY is the four-digit year
Note: If the current month on the device is December, the year data must be the current year or the following year. Otherwise, if the current month on the device is January through November, the year data must be the current year.

MM is the two digit month.

MM Valid Values: 01 to 12 with 01 representing January.

DD is the two-digit day of the month.

DD Valid Values: 01 to 31, depending on the value of MM.

HH is the two-digit hour in 24-hour time.

HH Valid Values: 00 to 23

MM is the two-digit minute of the hour.

MM Valid Values: 00 to 59

The following are examples of scheduling a load from different sources.

Example 1. Load modules and configuration source is a remote host:

Boot config>timedload activate
 
+------ BankA -----------+--------- Description ----------+------ Date -------+
| IMAGE - AVAIL          |                                | 01 Jan 1970 00:01 |
| CONFIG 1 - AVAIL       | test config for pubs           | 01 Jan 1970 01:26 |
| CONFIG 2 - AVAIL   *   | test config for pubs           | 01 Jan 1970 01:13 |
| CONFIG 3 - NONE        |                                | 01 Jan 1970 00:58 |
| CONFIG 4 - AVAIL       |                                | 01 Jan 1970 00:39 |
+------ BankB -----------+--------- Description ----------+------ Date -------+
| IMAGE - ACTIVE         |                                | 01 Jan 1970 00:01 |
| CONFIG 1 - AVAIL       | test config for pubs           | 01 Jan 1970 00:54 |
| CONFIG 2 - AVAIL       |                                | 01 Jan 1970 00:01 |
| CONFIG 3 - AVAIL       |                                | 01 Jan 1970 00:14 |
| CONFIG 4 - ACTIVE  *   |                                | 01 Jan 1970 00:24 |
 
+------------------------+--------------------------------+-------------------+
  * - Last Used Config      L - Config File is Locked
 
 
Time Activated Load Processing...
 
Select the bank to use:  (A, B): [A] a
Do you want to put load modules into the bank? (Yes, No, Quit): [Yes] yes
 
Do you want to retrieve a SINGLE image or a set of MODULES? [MODULES]? modules
 Specify the server IP address (dotted decimal): : [1.2.3.4] 192.9.200.1
Specify the remote modules directory: : (/u/bin) /usr/601bin/205img
The destination bank is bank A
TFTP SW load image
  get:   /usr/601bin/205img/
  from:  192.9.200.1
  to:    bank A.
tftp: connect to '192.9.200.1'
tftp: connect to '192.9.200.1'
tftp: connect to '192.9.200.1'
tftp: connect to '192.9.200.1'
tftp: connect to '192.9.200.1'
tftp: connect to '192.9.200.1'
tftp: connect to '192.9.200.1'
tftp: connect to '192.9.200.1'
tftp: connect to '192.9.200.1'
tftp: connect to '192.9.200.1'
tftp: connect to '192.9.200.1'
tftp: connect to '192.9.200.1'
tftp: connect to '192.9.200.1'
 
Operation completed successfully.
 
Do you want to put a configuration into the bank? (Yes, No, Quit): [Yes] yes
 
Specify the server IP address (dotted decimal): : [1.2.3.4] 192.9.200.1
Specify the remote file name: : (config.dat) /tftpboot/192.9.200.6.config
The destination bank is bank A
Select the destination configuration:  (1, 2, 3, 4): [1] 1
TFTP SW configuration file
  get:   /tftpboot/192.9.200.6.config
  from:  192.9.200.1
  to:    bank A, configuration 1.
tftp: connect to '192.9.200.1'
 
Operation completed successfully.
 
Time of day to load the router (YYYYMMDDHHMM) []? 199706261630
The load timer has been activated.
Boot config>

Example 2. Load modules and configuration source is a bank:

Boot config>timedload activate
 
+------ BankA -----------+--------- Description ----------+------ Date -------+
| IMAGE - AVAIL          |                                | 01 Jan 1970 00:01 |
| CONFIG 1 - AVAIL       | test config for pubs           | 01 Jan 1970 01:26 |
| CONFIG 2 - AVAIL   *   | test config for pubs           | 01 Jan 1970 01:13 |
| CONFIG 3 - NONE        |                                | 01 Jan 1970 00:58 |
| CONFIG 4 - AVAIL       |                                | 01 Jan 1970 00:39 |
+------ BankB -----------+--------- Description ----------+------ Date -------+
| IMAGE - ACTIVE         |                                | 01 Jan 1970 00:01 |
| CONFIG 1 - AVAIL       | test config for pubs           | 01 Jan 1970 00:54 |
| CONFIG 2 - AVAIL       |                                | 01 Jan 1970 00:01 |
| CONFIG 3 - AVAIL       |                                | 01 Jan 1970 00:14 |
| CONFIG 4 - ACTIVE  *   |                                | 01 Jan 1970 00:24 |
 
+------------------------+--------------------------------+-------------------+
  * - Last Used Config      L - Config File is Locked
 
Time Activated Load Processing...
 
Select the bank to use:  (A, B): [A] a
Do you want to put load modules into the bank? (Yes, No, Quit): [Yes] no
 
Do you want to put a configuration into the bank? (Yes, No, Quit): [Yes] no
 
Select the configuration to use:  (1, 2, 3, 4): [1] 1
 
Time of day to load the router (YYYYMMDDHHMM) []? 199706261630
The load timer has been activated.
Boot config>

deactivate

Cancels a scheduled load.

Example 1: Deactivate the time activated load

Boot config>timedload deactivate
Deactivate Load Timer Processing...
 
Do you want to deactivate the load timer? (Yes, No, Quit): [No] yes
The load timer has been deactivated.
Boot config>

view

Displays scheduled load information.

Boot Config> timedload view
Time Activated Load Schedule Information...
 
The router is scheduled to reload as follows.
 
Date:  June 26, 1997
Time:  16:30
The load modules are in bank A.
The configuration is CONFIG 1 in bank A.
Boot config>

Unlock

Use the unlock command to allow the device to overwrite the selected configuration that was previously locked.

Syntax:

unlock

Example: Boot config>unlock

+------ BankA -----------+--------- Description ----------+------ Date -------+
| IMAGE - NONE           |                                | 01 Jan 1970 01:03 |
| CONFIG 1 - AVAIL       | test config for pubs           | 01 Jan 1970 00:13 |
| CONFIG 2 - AVAIL   *   | test config for pubs           | 01 Jan 1970 01:13 |
| CONFIG 3 - NONE        |                                | 01 Jan 1970 00:58 |
| CONFIG 4 - AVAIL    L  |                                | 01 Jan 1970 00:26 |
+------ BankB -----------+--------- Description ----------+------ Date -------+
| IMAGE - ACTIVE         |                                | 01 Jan 1970 00:01 |
| CONFIG 1 - AVAIL       | test config for pubs           | 01 Jan 1970 00:54 |
| CONFIG 2 - AVAIL       |                                | 01 Jan 1970 00:01 |
| CONFIG 3 - AVAIL       |                                | 01 Jan 1970 00:14 |
| CONFIG 4 - ACTIVE  *   |                                | 01 Jan 1970 00:24 |
 
+------------------------+--------------------------------+-------------------+
  * - Last Used Config      L - Config File is Locked
 
 
Select the source bank:  (A, B): [A]
 
Select the source configuration:  (1, 2, 3, 4): [1] 4
Attempting to unlock bank A and configuration 4.
 
Operation completed successfully.
Boot config>list
+------ BankA -----------+--------- Description ----------+------ Date -------+
| IMAGE - NONE           |                                |                   |
| CONFIG 1 - AVAIL       | test config for pubs           | 01 Jan 1970 00:01 |
| CONFIG 2 - AVAIL   *   | test config for pubs           | 01 Jan 1970 01:13 |
| CONFIG 3 - NONE        |                                | 01 Jan 1970 00:58 |
| CONFIG 4 - AVAIL       |                                | 01 Jan 1970 00:14 |
+------ BankB -----------+--------- Description ----------+------ Date -------+
| IMAGE - ACTIVE         |                                | 01 Jan 1970       |
| CONFIG 1 - AVAIL       | test config for pubs           | 01 Jan 1970 00:54 |
| CONFIG 2 - AVAIL       |                                | 01 Jan 1970 00:01 |
| CONFIG 3 - AVAIL       |                                | 01 Jan 1970 00:14 |
| CONFIG 4 - ACTIVE  *   |                                | 01 Jan 1970 00:24 |
 
+------------------------+--------------------------------+-------------------+
  * - Last Used Config      L - Config File is Locked
 
  Auto-boot mode is enabled.  Fast-boot mode is disabled.

Note:

Note that bank A config 4 is no longer marked with an "L."

Update-firmware

Use the update-firmware command to install the Firm.ld load module that you have received on either Bank A or Bank B of your 2216.

Rebooting will not occur automatically after this command is executed. You must set the bank you want to reboot from using the Boot config> set command, and the new firmware will be updated when you reboot. See "Accessing the Firmware from the Command Line Interface" for rebooting information.

Syntax:

update-firmware

Example:

Boot config>update
+-------------------------+-------------------------+
 |         BANK A          |         BANK B          |
 | Product ID -   2216-MAS | Product ID -   2216-MAS |
 | Version   3 Release   1 | Version   3 Release   1 |
 | Mod       0 PTF       0 | Mod       0 PTF       0 |
 | Feat.  2807 RPQ       0 | Feat.  2807 RPQ       0 |
 | Date  14 Jul 1998 07:45 | Date   7 Aug 1998 14:05 |
 | Build           cc_155b | Build           cc_158b |
 |                         |               test-load |
 +-------------------------+-------------------------+
 
 DO NOT POWER OFF while firmware is updating.
 To exit, type Ctrl-c at the Select bank/restore prompt.
 
 Select the source bank or P to restore from Precover.img:  (A, B, P): [A]B
 
 Using Local Firmware image /hd0/sys1/Firm.ld
 flash: ID = 0x01A4, sector wp = 0x00
 flash: Found /hd0/sys1/Firm.ld:524774 bytes.
 flash: Loading file /hd0/sys1/Firm.ld...
 flash: File /hd0/sys1/Firm.ld loaded at 0x0025f0ec for 524288 bytes
 flash: Creating /hd0/precover.img from flash
 flash: Recovery image created.
 flash: Validating firmware image
 flash: Update from:0025F0EC, offset=00010000, flash size=524288
 flash: Erasing sector 7f
 flash: Erasing sector 3f
 flash: Erasing sector 1f
 flash: Erasing sector  f
 flash: Erasing sector  7
 flash: Erasing sector  3
 flash: Erasing sector  1
 flash: Current addr = 0007f000
 
 Operation completed successfully.

[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]